-
Notifications
You must be signed in to change notification settings - Fork 201
New overloads for WriteStringAsync and WriteBytesAsync method which takes CancellationToken #1111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the new overload we are exposing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the other new overload we are exposing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good catch!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is still grammatically correct, but if you want to match the other summaries this is missing an 's' (writes not write).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good eye 🔍. Fixed.
508f694 to
f6b0d64
Compare
|
/check-enforcer evaluate |
|
/check-enforcer reset |
Fixes #1078
Exposing 2 new overloads which internally calls the
Stream.WriteAsyncoverload which takes a CancellationToken instanceNot bumping up package version as I think we can club this change with other ones.